View RXM-GPS-SG-T_1082835.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

description the sg series gps receiver module is a self- contained high-performance gps receiver with an on-board lna and saw filter. based on the sirfstar iii chipset, it provides exceptional sensitivity, even in dense foliage and urban canyons. the module?s very low power consumption helps maximize runtimes in battery powered applications. with over 200,000 effective correlators, the sg series receiver can acquire and track up to 20 satellites simultaneously in just seconds, even at the lowest signal levels. housed in a compact reflow-compatible smd package, the receiver requires no programming or additional rf components (except an antenna) to form a complete gps solution. these features, along with the module?s standard nmea data output, make the sg series easy to integrate, even by engineers without previous rf or gps experience. sg series gps receiver module data guide wireless made simple ? revised 6/28/10 figure 1: package dimensions gp s module rxm-gp s - s g lot grxxxx 0.591 (15.00) 0.512 (13.00) 0.0 8 7 (2.20) applications include n positioning and navigation n location and tracking n security/loss-prevention n surveying n logistics n fleet management n sirf star iii chipset n 200,000+ correlators n low power consumption (46mw) n high sensitivity (-159dbm) n 20 channels n fast ttff at low signal levels n battery-backed sram n no programming necessary n no external rf components needed (except an antenna) n no production tuning n direct serial interface n power down feature n compact surface-mount package n manual or reflow compatible n rohs compliant features part # description rxm-gps-sg-x gps receiver module mdev-gps-sg master development system x = ?t? for tape and reel, ?b? for bulk reels are 1,000 pcs. quantities less than 1,000 pcs. are supplied in bulk ordering information rxm-gps-sg
electrical specifications *caution* this product incorporates numerous static-sensitive components. always wear an esd wrist strap and observe proper esd handling procedures when working with this device. failure to observe this precaution may result in module damage or failure. absolute maximum ratings supply voltage v cc +6.5 vdc input battery backup voltage +7.0 vdc 2.85v output current 50 ma operating temperature - 3 0 to +85 c storage temperature -40 to +125 c soldering temperature +225c for 10 seconds *note* exceeding any of the limits of this section may lead to permanent damage to the device. furthermore, extended operation at these maximum ratings may reduce the life of this device. table 1: sg series receiver specifications parameter designation min. typical max. units notes power supply supply voltage v cc 3 .0 ? 4.2 vdc 1 supply current: i cc 2 peak ? ? 46.0 ma ? acquisition ? 3 2?ma? tracking ? 28 ? ma ? standby ? 1.5 ? ma ? backup battery voltage v bat 1. 3 ?6.0vdc? backup battery current i bat ? ? 10 a ? 2.85v output voltage v out 2.79 2.85 2.91 vdc ? 2.85v output current i out ?? 3 0ma 3 output logic low voltage v ol ? ? 0.25*v out vdc ? output logic high voltage v oh 0.75*v out ??vdc? output logic low current i ol ?2?ma? output logic high current i oh ?2?ma? input logic low voltage v il -0. 3 ?0. 3 *v out vdc ? input logic high voltage v ih 0.7*v out ? 3 .6 vdc ? input logic low current i il -10 ? 10 a ? with pull-down ? ? 60 a ? input logic high current i ih -10 ? 10 a ? with pull-down ? ? 60 a ? input capacitance c in ??4pf? output capacitance c out ??4pf4 lna section insertion power gain |s 21 | 2 ?18?db5 noise figure nf ? 0.9 ? db 5 antenna port rf input impedance r in ?50? ? environmental operating temperature range ? - 3 0 ? +85 c? storage temperature range ? -40 25 +85 c? receiver section receiver sensitivity tracking ? -159 ? dbm ? cold start ? -144 ? dbm ? acquisition time hot start (open sky) ? ? 2 s ? hot start (indoor) ? ? 15 s ? cold start ? 3 5?s? position accuracy autonomous ? ? 10 m ? sbas ? ? 5 m ? altitude ? ? 60,000 ft ? velocity ? ? 1,000 knots ? chipset sirf star iii, gsc 3 f/lpx 7990 firmware version gsw 3 .5.0_ 3 .5.00.00-sdk- 3 ep2.01a frequency l1 1575.42mhz, c/a code channels 20 update rate 1hz protocol support nmea 018 3 ver 3 .0, sirf binary page 2 page 3 online resources ? latest news ? data guides ? application notes ? knowledgebase ? software updates if you have questions regarding this or any linx product make www.linxtechnologies.com your first stop. day or night, the linx website gives you instant access to the latest information regarding the products and services of linx. it?s all here: manual and software updates, application notes, a comprehensive knowledgebase, fcc information, and much more. here you will find the answers you need arranges in an intuitive format. be sure to visit often! ? www.linxtechnologies.com notes: 1. i out = 0 2. v cc = 3 . 3 v, i out = 0 3 . v cc = 3 . 3 v 4. output buffer 5. at 25 c
pin assignments rxb 1 txb 2 1pp s 3 txa 4 rxa 5 gnd 21 gpio10 6 lckind 7 gpio1 8 rfpwrup 9 on_off 10 gnd 20 rfin 19 gnd 1 8 vout 17 boot s el 16 gnd 22 gpio13 15 gpio15 14 gpio14 13 vcc 12 vbackup 11 figure 2: sg series receiver pinout (top view) pin # name i/o description 1 rxb i serial input for channel b (default null) 2 txb o serial output for channel b (default null) 3 1pps o pulse per second (1us pulse) 4 txa o serial output for channel a (default nmea) 5 rxa i serial input for channel a (default nmea) 6 gpio10 i/o general purpose i/o 7 lckind o lock indicator 8 gpio1 i/o general purpose i/o 9 rfpwrup o indicate power state 10 on_off i edge triggered soft on/off request. should only be used to wake up the module when the rfpwrup line is low. 11 vbackup p backup battery supply voltage. this line must be powered to enable the module. 12 vcc p supply voltage 1 3 gpio14 i/o general purpose i/o 14 gpio15 i/o general purpose i/o 15 gpio1 3 i/o general purpose i/o 16 bootsel i boot mode select (do not connect in normal operation) 17 vout p 2.85v linear regulator power output 18,20-22 gnd p ground 19 rfin i gps rf signal input pin descriptions a brief overview of gps the global positioning system (gps) is a u.s.-owned utility that freely and continuously provides positioning, navigation, and timing (pnt) information. originally created by the u.s. department of defense for military applications, the system was made available without charge to civilians in the early 1980s. the global positioning system consists of a nominal constellation of 24 satellites orbiting the earth at about 12,000 nautical miles in height. the pattern and spacing of the satellites allow at least four to be visible above the horizon from any point on the earth. each satellite transmits low power radio signals which contain three different bits of information; a pseudorandom code identifying the satellite, ephemeris data which contains the current date and time as well as the satellite?s health, and the almanac data which tells where each satellite should be at any time throughout the day. a gps receiver such as the linx sg series gps module receives and times the signals sent by multiple satellites and calculates the distance to each satellite. if the position of each satellite is known, the receiver can use triangulation to determine its position anywhere on the earth. the receiver uses four satellites to solve for four unknowns; latitude, longitude, altitude, and time. if any of these factors is already known to the system, an accurate position (fix) can be obtained with fewer satellites in view. tracking more satellites improves calculation accuracy. in essence, the gps system provides a unique address for every square meter on the planet. a faster time to first fix (ttff) is also possible if the satellite information is already stored in the receiver. if the receiver knows some of this information, then it can accurately predict its position before acquiring an updated position fix. for example, aircraft or marine navigation equipment may have other means of determining altitude, so the gps receiver would only have to lock on to three satellites and calculate three equations to provide the first position fix after power-up. ttff is often broken down into three parts: cold: a cold start is when the receiver has no accurate knowledge of its position or time. this happens when the receiver?s internal real time clock (rtc) has not been running or it has no valid ephemeris or almanac data. in a cold start, the receiver takes 3 5 to 40 seconds to acquire its position. if new almanac data is required, this may take up to 15 minutes (see page 22 for more details). warm or normal: a typical warm start is when the receiver has valid almanac and time data and has not significantly moved since its last valid position calculation. this happens when the receiver has been shut down for more than 2 hours, but still has its last position, time, and almanac saved in memory, and its rtc has been running. the receiver can predict the location of the current visible satellites and its location; however, it needs to wait for an ephemeris broadcast (every 3 0 seconds) before it can accurately calculate its position. hot or standby: a hot start is when the receiver has valid ephemeris, time, and almanac data. this happens when the receiver has been shut down for less than 2 hours and has the necessary data stored in memory with the rtc running. in a hot start, the receiver takes 1 to 2 seconds to acquire its position. the time to calculate a fix in this state is sometimes referred to as time to subsequent fix or ttsf. page 4 page 5
module description the sg series is a high performance self-contained gps receiver in a compact rohs compliant surface mount package. the module is based on the sirfstar iii low power chipset, which consumes significantly less power than competitive products while providing exceptional performance even in dense foliage and urban canyons. the module includes an internal saw filter and lna, so no external rf components are needed other than an antenna. the simple serial interface and industry standard nmea protocol make integration of the sg series receiver into an end product or system extremely straightforward. the module?s high-performance rf architecture allows it to receive gps signals that are as low as -159dbm. with over 200,000 effective correlators, the sg series can track up to 20 satellites at the same time. once locked onto the visible satellites, the receiver calculates the range to the satellites and determines its position and the precise time. it then outputs the data through a standard serial port using several standard nmea protocol formats. the gps core handles all of the necessary initialization, tracking, and calculations autonomously, so no programming is required. the rf section is optimized for low level signals, and requires no production tuning of any type. antenna considerations the sg series module is designed to utilize a wide variety of external antennas. the module has a regulated power output which simplifies the use of gps antenna styles which require external power. this allows the designer great flexibility, but care must be taken in antenna selection to ensure optimum performance. for example, a handheld device may be used in many varying orientations so an antenna element with a wide and uniform pattern may yield better overall performance than an antenna element with high gain and a correspondingly narrower beam. conversely, an antenna mounted in a fixed and predictable manner may benefit from pattern and gain characteristics suited to that application. evaluating multiple antenna solutions in real-world situations is a good way to rapidly assess which will best meet the needs of your application. for gps, the antenna should have good right hand circular polarization characteristics (rhcp) to match the polarization of the gps signals. ceramic patches are the most commonly used style of antenna, but there are many different shapes, sizes and styles of antennas available. regardless of the construction, they will generally be either passive or active types. passive antennas are simply an antenna tuned to the correct frequency. active antennas add a low noise amplifier (lna) after the antenna and before the module to amplify the weak gps satellite signals. for active antennas, the vout line can provide 2.85v at 3 0ma to power the external lna. a 3 00 ohm ferrite bead should be used to connect this line to the rfin line. this bead will prevent the rf from getting into the power supply, but will allow the dc voltage onto the rf trace to feed into the antenna. a series capacitor inside the module prevents this dc voltage from affecting the bias on the module?s internal lna. maintaining a 50 ohm path between the module and antenna is critical. errors in layout can significantly impact the module?s performance. please review the layout guidelines elsewhere in this guide carefully to become more familiar with these considerations. backup battery the sg series module is designed to work with a backup battery that keeps the sram memory and the rtc powered when the rf section and the main gps core are powered down. this enables the module to have a faster time to first fix (ttff) when the module is powered back on. the memory and clock pull about 10a. this means that a small lithium battery is sufficient to power these sections. this significantly reduces the power consumption and extends the main battery life while allowing for fast position fixes when the module is powered back on. power supply requirements the module requires a clean, well-regulated power source. while it is preferable to power the unit from a battery, it can operate from a power supply as long as noise is less than 20mv. power supply noise can significantly affect the receiver?s sensitivity, therefore providing clean power to the module should be a high priority during design. bypass capacitors should be placed as close as possible to the module. the values should be adjusted depending on the amount and type of noise present on the supply line. the 1pps output the 1pps line outputs 1 pulse per second on the rising edge of the gps second when the receiver has an over-solved navigation solution from five or more satellites. the pulse has a duration of 1s and an accuracy of about 1s from the gps second. this line is low if the receiver is not able to acquire an over- solved navigation solution (a lock on more than 4 satellites). the gps second is based on the atomic clocks in the gps satellites, which are monitored and set to universal time master clocks. this output and the time calculated from the gps satellite transmissions can be used as a clock feature in an end product. the lock indicator line the lock indicator line outputs a series of 100ms pulses with a 50% duty cycle when the module is searching for a fix. once the receiver acquires a solution, the line outputs a single 100ms pulse every second. this line can be connected to a microcontroller to monitor the state of the module, or connected to an led as a visual indicator. volt a ge s econd s 0 1 po s ition fixed s e a rching for fix volt a ge s econd s 0 1 figure 3 : sg series lock indicator signals page 6 page 7
page 9 typical applications figure 4 shows a circuit using the gps module with a passive antenna. figure 5 shows a circuit using the gps module with an active antenna. rxb 1 txb 2 1pp s 3 txa 4 rxa 5 gnd 21 gpio10 6 lckind 7 gpio1 8 rfpwrup 9 on_off 10 gnd 20 rfin 19 gnd 1 8 vout 17 boot s el 16 gnd 22 gpio13 15 gpio15 14 gpio14 13 vcc 12 vbackup 11 p tx rx gnd vcc gnd gnd vcc gnd vcc gnd figure 4: sg series module with a passive antenna rxb 1 txb 2 1pp s 3 txa 4 rxa 5 gnd 21 gpio10 6 lckind 7 gpio1 8 rfpwrup 9 on_off 10 gnd 20 rfin 19 gnd 1 8 vout 17 boot s el 16 gnd 22 gpio13 15 gpio15 14 gpio14 13 vcc 12 vbackup 11 p tx rx gnd vcc gnd gnd vcc gnd vcc gnd 300 ferrite be a d figure 5: sg series module with an active antenna page 8 power control the sg series has a built-in power control mode called adaptive trickle power mode. in this mode, the receiver will power on at full power to acquire and track satellites and obtain satellite data. it then powers off the rf stage and only uses its processor stage (cpu) to determine a position fix (which takes about 160ms). once the fix is obtained, the receiver goes into a low power standby state. after a user-defined period of time, the receiver wakes up to track the satellites for a user-defined period of time, updates its position using the cpu only, and then resumes standby. the initial acquisition time is variable, depending on whether it is a cold start or assisted, but a maximum acquisition time is definable. this cycling of power is ideal for battery-powered applications since it significantly reduces the amount of power consumed by the receiver while still providing similar performance to the full power mode. in normal conditions, this mode provides a fixed power savings, but under poor signal conditions, the receiver returns to full power to improve performance. the receiver sorts the satellites according to signal strength and if the fourth satellite is below 26db-hz, then the receiver switches to full power. once the fourth satellite is above 3 0db-hz, the receiver returns to adaptive trickle power mode. for optimum performance, sirf recommends cycle times of 3 00ms track to 1s interval or 400ms track to 2s interval. cpu time is about 160ms to compute the navigation solution and empty the uart. there are some situations in which the receiver stays in full power mode. these are: to collect periodic ephemeris data, to collect periodic ionospheric data, to perform rtc convergence, and to improve the navigation result. depending on states of the power management, the receiver will be in one of three system states: full power state all rf and baseband circuitry are fully powered. there is a difference in power consumption during acquisition mode and tracking mode. acquisition requires more processing, so it consumes more power. this is the initial state of the receiver and it stays in this state until a reliable position solution is achieved. cpu only state this state is entered when the satellite measurements have been collected but the navigation solution still needs to be computed. the rf and dsp processing are no longer needed and can be turned off. stand-by state in this state, the rf section is completely powered off and the clock to the baseband is stopped. about 1ma of current is drawn in this state for the internal core regulator, rtc and battery-backed ram. the receiver enters this state when a position fix has been computed and reported. the table below shows the rfpwrup and vout conditions in each power state. power state rfpwrup vout full power h enabled cpu only h enabled stand by l enabled hibernate l disabled table 2: rfpwrup and vout conditions
nmea output messages the following sections outline the data structures of the various nmea protocols that are supported by the module. by default, the nmea commands are output at 9,600bps, 8 data bits, no parity, and 1 stop bit. gga ? global positioning system fixed data the table below contains the values for the following example: $gpgga,05 3 740.000,250 3 .6 3 19,n,121 3 6.0099,e,1,08,1.1,6 3 .8,m,15.2,m,,0000*64 name example units description message id $gpgga gga protocol header utc time 05 3 740 hhmmss.sss latitude 250 3 .6 3 19 ddmm.mmmm n/s indicator n n=north or s=south longitude 121 3 6.0099 dddmm.mmmm e/w indicator e e=east or w=west position fix indicator 1 see table 4 satellites used 08 range 0 to 12 hdop 1.1 horizontal dilution of precision msl altitude 6 3 .8 meters units m meters geoid separation 15.2 meters units m meters age of diff. corr. second null fields when dgps is not used diff. ref. station id 0000 checksum *64 end of message termination value description 0 fix not available or invalid 1 gps sps mode, fix valid 2 differential gps, sps mode, fix valid (not supported) 3 -5 not supported 6 dead reckoning mode, fix valid table 3 : global positioning system fixed data example table 4: position indicator values page 10 page 11 protocols linx gps modules use the sirfstar iii chipset. this chipset allows two protocols to be used, nmea-018 3 and sirf binary. switching between the two is handled using a single serial command. the nmea protocol uses ascii characters for the input and output messages and provides the most common features of gps development in a small command set. the sirf binary protocol uses byte data types and allows more detailed control over the gps receiver and its functionality using a much larger command set. although both protocols have selectable baud rates, it?s recommended that sirf binary use baud rates of 3 8,400bps or higher. for a detailed description of the sirf binary protocol, see the sirf binary protocol reference manual, available from sirf technology, inc. although sirf binary protocol may be used with the module, linx only offers tech support for the nmea protocol. interfacing with nmea messages linx modules default to the nmea protocol. output messages are sent from the receiver on the txa pin and input messages are sent to the receiver on the rxa pin. by default, output messages are sent once every second. details of each message are described in the following sections. the nmea message format is as follows: . the serial data structure defaults to 9,600bps, 8 data bits, 1 stop bit, and no parity bits. each message starts with a $ character and ends with a . all fields within each message are separated by a comma. the checksum follows the * character and is the last two characters, not including the . it consists of two hex digits representing the exclusive or (xor) of all characters between, but not including, the $ and * characters. when reading nmea output messages, if a field has no value assigned to it, the comma will still be placed following the previous comma. for example, {,04,,,,,2.0,} shows four empty fields between values 04 and 2.0. when writing nmea input messages, all fields are required, none are optional. an empty field will invalidate the message and it will be ignored. reading nmea output messages: ? initialize a serial interface to match the serial data structure of the gps receiver. ? read the nmea data from the txa pin into a receive buffer. ? separate it into six buffers, one for each message type. use the characters ($) and as end points for each message. ? for each message, calculate the checksum as mentioned above to compare with the checksum received. ? parse the data from each message using commas as field separators. ? update the application with the parsed field values. ? clear the receive buffer and be ready for the next set of nmea messages. writing nmea input messages: ? initialize a serial interface to match the serial data structure of the gps receiver. ? assemble the message to be sent with the calculated checksum. ? transmit the message to the receiver on the rxa pin.
gsv ? gnss satellites in view the table below contains the values for the following example: $gpgsv, 3 ,1,12,28,81,285,42,24,67, 3 02,46, 3 1,54, 3 54,,20,51,077,46*7 3 $gpgsv, 3 ,2,12,17,41, 3 28,45,07, 3 2, 3 15,45,04, 3 1,250,40,11,25,046,41*75 $gpgsv, 3 , 3 ,12,08,22,214, 3 8,27,08,190,16,19,05,092, 33 ,2 3 ,04,127,*7b 1. depending on the number of satellites tracked, multiple messages of gsv data may be required. name example units description message id $gpgsv gsv protocol header total number of messages 1 3 range 1 to 3 message number 1 1 range 1 to 3 satellites in view 12 satellite id 28 channel 1 (range 01 to 3 2) elevation 81 degrees channel 1 (range 00 to 90) azimuth 285 degrees channel 1 (range 000 to 3 59) snr (c/no) 42 db-hz channel 1 (range 00 to 99, null when not tracking) satellite id 20 channel 4 (range 01 to 3 2) elevation 51 degrees channel 4 (range 00 to 90) azimuth 77 degrees channel 4 (range 000 to 3 59) snr (c/no) 46 db-hz channel 4 (range 00 to 99, null when not tracking) checksum *7 3 end of message termination table 8: gnss satellites in view example page 12 page 1 3 gll ? geographic position ? latitude / longitude the table below contains the values for the following example: $gpgll,250 3 .6 3 19,n,121 3 6.0099,e,05 3 740.000,a,a*52 gsa ? gnss dop and active satellites the table below contains the values for the following example: $gpgsa,a, 3 ,24,07,17,11,28,08,20,04,,,,,2.0,1.1,1.7* 3 5 name example units description message id $gpgll gll protocol header latitude 250 3 .6 3 19 ddmm.mmmm n/s indicator n n=north or s=south longitude 121 3 6.0099 dddmm.mmmm e/w indicator e e=east or w=west utc time 05 3 740 hhmmss.sss status a a=data valid or v=data not valid mode a a=autonomous, d=dgps, e=dr checksum *52 end of message termination name example units description message id $gpgsa gsa protocol header mode1 a see table 7 mode 2 3 1=no fix, 2=2d, 3 = 3 d id of satellite used 24 sv on channel 1 id of satellite used 7 sv on channel 2 ... ... id of satellite used sv on channel 12 pdop 2 position dilution of precision hdop 1.1 horizontal dilution of precision vdop 1.7 vertical dilution of precision checksum * 3 5 end of message termination table 5: geographic position ? latitude / longitude example table 6: gnss dop and active satellites example value description m manual - forced to operate in 2d or 3 d mode a automatic - allowed to automatically switch 2d/ 3 d table 7: mode1 values
nmea input messages the following outlines the serial commands input into the module for configuration. by default, the commands are input at 9,600bps, 8 data bits, no parity, and 1 stop bit. all fields in all proprietary nmea messages are required; none are optional. all nmea messages are comma delimited. the table below outlines the message identifiers supported by the module. 1. input coordinates must be wgs84 name example description start sequence $psrf message id message identifier consisting of three numeric characters. input messages begin at mid 100. payload data message specific data. checksum cksum cksum is a two-hex character checksum as defined in the nmea specification, nmea-018 3 standard for interfacing marine electronic devices. checksums are required on all input messages. end sequence each message must be terminated using carriage return (cr) line feed (lf) (\r\n, 0x0d0a) to cause the receiver to process the input message. they are not printable ascii characters, so are omitted from the examples. message mid description setserialport 100 set port a parameters and protocol navigationinitialization 101 parameters required for start using x/y/z 1 query/rate control 10 3 query standard nmea message and/or set output rate llanavigationinitialization 104 parameters required for start using lat/lon/alt 1 development data on/off 105 development data messages on/off select datum 106 selection of datum to be used for coordinate transformations powermanagement 200 sets the power performance of the receiver setio 211 sets the i/o lines to an input or output readinput 212 reads the state of the inputs lines writeoutput 21 3 writes the state of an output line query 214 get configuration and last state of all gpios table 11: serial data structure table 12: message id values page 14 page 15 rmc ? recommended minimum specific gnss data the table below contains the values for the following example: $gprmc,05 3 740.000,a,250 3 .6 3 19,n,121 3 6.0099,e,2.69,79.65,100106,,,a*5 3 vtg ? course over ground and ground speed the table below contains the values for the following example: $gpvtg,79.65,t,,m,2.69,n,5.0,k,a* 3 8 name example units description message id $gprmc rmc protocol header utc time 5 3 740 hhmmss.sss status a a=data valid or v=data not valid latitude 250 3 .6 3 2 ddmm.mmmm n/s indicator n n=north or s=south longitude 121 3 6.01 dddmm.mmmm e/w indicator e e=east or w=west speed over ground 2.69 knots true course over ground 79.65 degrees date 100106 ddmmyy magnetic variation degrees variation sense e=east or w=west (not shown) mode a a=autonomous, d=dgps, e=dr checksum *5 3 end of message termination table 9: recommended minimum specific gnss data example table 10: course over ground and ground speed example name example units description message id $gpvtg vtg protocol header course over ground 79.65 degrees measured heading reference t true course over ground degrees measured heading reference m magnetic speed over ground 2.69 knots measured speed units n knots speed over ground 5 km/hr measured speed units k kilometer per hour mode a a=autonomous, e=dr checksum * 3 8 end of message termination
101 ? navigationinitialization this command is used to initialize the receiver by providing current position (in x, y, z coordinates), clock offset, and time. this enables the receiver to search for the correct satellite signals at the correct signal parameters. correct initialization parameters enable the receiver to acquire signals quickly. the table below contains the values for the following example: start using known position and time $psrf101,-2686700,-4304200,3851624,96000,497260,921,12,3*2f 1. use 0 for last saved value if available. if this is unavailable, a default value of 96000 is used. name example units description message id $psrf101 psrf101 protocol header ecef x -2686700 meters x coordinate position ecef y -4304200 meters y coordinate position ecef z 3851624 meters z coordinate position clkoffset 96000 hz clock offset of the evaluation receiver 1 timeofweek 497260 seconds gps time of week weekno 921 gps week number channelcount 12 range 1 to 12 resetcfg 3 see table 15 checksum *2f end of message termination hex description 0x01 hot start ? all data valid 0x02 warm start ? ephemeris cleared 0x03 warm start (with init) ? ephemeris cleared, initialization data loaded 0x04 cold start ? clears all data in memory 0x08 clear memory ? clears all data in memory and resets the receiver back to factory defaults table 14: navigationinitialization example table 15: resetcfg values page 16 page 17 100 ? setserialport this command message is used to set the protocol (sirf binary or nmea) and/or the communication parameters (baud rate, data bits, stop bits, and parity). generally, this command is used to switch the module back to sirf binary protocol mode where a more extensive command message set is available. when a valid message is received, the parameters are stored in battery-backed sram and the receiver restarts using the saved parameters. the table below contains the values for the following example: switch to sirf binary protocol at 9600,8,n,1 $psrf100,0,9600,8,1,0*0c 1. sirf protocol is only valid for 8 data bits, 1 stop bit, and no parity. for details on the sirf binary protocol, please refer to sirf?s binary protocol reference manual. name example description message id $psrf100 psrf100 protocol header protocol 0 0=sirf binary, 1=nmea baud 9,600 4800, 9600, 19200, 38400, 57600 databits 8 8,7 1 stopbits 1 0,1 1 parity 0 0=none, 1=odd, 2=even 1 checksum *0c end of message termination table 13: setserialport example
104 ? llanavigationinitialization this command is used to initialize the receiver by providing current position (in latitude, longitude, and altitude coordinates), clock offset, and time. this enables the receiver to search for the correct satellite signals at the correct signal parameters. correct initialization parameters enable the receiver to acquire signals quickly. the table below contains the values for the following example: start using known position and time. $psrf104, 3 7. 3 875111,-121.972 3 2,0,96000,2 3 7759,1946,12,1*06 1. use 0 for last saved value if available. if this is unavailable, a default value of 96000 is used. name example units description message id $psrf104 psrf104 protocol header latitude 3 7. 3 875111 degrees latitude position (range 90 to ?90) longitude -121.972 3 2 degrees longitude position (range 180 to ?180) altitude 0 meters altitude position clkoffset 96000 hz clock offset of the evaluation receiver 1 timeofweek 2 3 7759 seconds gps time of week weekno 1946 extended gps week number (1024 added) channelcount 12 range 1 to 12 resetcfg 1 see table 20 checksum *06 end of message termination hex description 0x01 hot start ? all data valid 0x02 warm start ? ephemeris cleared 0x0 3 warm start (with init) ? ephemeris cleared, initialization data loaded 0x04 cold start ? clears all data in memory 0x08 clear memory ? clears all data in memory and resets receiver back to factory defaults table 19: llanavigationinitialization example table 20: resetcfg values 103 ? query/rate control this command is used to control the output of standard nmea messages gga, gll, gsa, gsv, rmc, and vtg. using this command message, standard nmea messages may be polled once, or setup for periodic output. checksums may also be enabled or disabled depending on the needs of the receiving program. nmea message settings are saved in battery-backed memory for each entry when the message is accepted. the table below contains the values for the following example: 1. query the gga message with checksum enabled $psrf10 3 ,00,01,00,01*25 2. enable vtg message for a 1 hz constant output with checksum enabled $psrf10 3 ,05,00,01,01*20 3 . disable vtg message $psrf10 3 ,05,00,00,01*21 name example units description message id $psrf10 3 psrf10 3 protocol header msg 0 see table 18 mode 1 0=setrate, 1=query rate 0 seconds output ? off=0, max=255 cksumenable 1 0=disable, 1=enable checksum checksum *25 end of message termination value description 0 gga 1 gll 2 gsa 3 gsv 4 rmc 5 vtg 6 mss (not supported) 7 not defined 8 zda 9 not defined table 17: query/rate control example table 18: msg values page 18 page 19
200 ? powermanagement the table below contains the values for the following example to set the receiver to adaptive trickle power mode: $plsc,200,2, 3 00,1000, 3 00000, 3 0000*0e the table below lists the possible values for the mode section of this command. name example units description mid $plsc,200 message id mode 2 see table 24 ontime 3 00 (200 - 900) ms must be > 200ms and a multiple of 100 (if not, it is rounded up to the nearest multiple of 100). lp interval 1000 (1000 - 214748 3 000) ms must be an integer value greater than or equal to 1000. maxacqtime 3 00000 (1000 - 214748 3 000) ms when adaptive trickle power is enabled, this is the maximum allowable time from the start of a power cycle to the time a valid position fix is obtained. if no fix is obtained in this time, the receiver is deactivated for up to maxofftime, and a hot start is commanded when the receiver reactivates. the integer must be in multiples of 1000ms. maxofftime 3 0000 (1000 - 1800000) ms the longest period (in ms) for which the receiver deactivates due to the maxacqtime timeout. the actual deactivated period may be less if the user- specified duty cycle (ontime / lpinterval) can be maintained. checksum *0e end of message termination value description 0 ask receiver to send current power mode 1 set receiver to full power mode 2 set receiver to adaptive trickle power mode table 2 3 : power management command example table 24: mode values 105 ? development data on/off use this command to enable development data information if you are having trouble getting commands accepted. invalid commands generate debug information that enables you to determine the source of the command rejection. common reasons for input command rejection are invalid checksum or parameter out of specified range. the table below contains the values for the following example: 1. debug on $psrf105,1* 3 e 2. debug off $psrf105,0* 3 f 106 ? select datum $psgps receivers perform initial position and velocity calculations using an earth-centered earth-fixed (ecef) coordinate system. results may be converted to an earth model (geoid) defined by the selected datum. the default datum is wgs 84 (world geodetic system 1984) which provides a worldwide common grid system that may be translated into local coordinate systems or map datums. (local map datums are a best fit to the local shape of the earth and not valid worldwide.) the table below contains the values for the following example: datum select tokyo_mean $psrf106,178* 3 2 name example units description message id $psrf105 psrf105 protocol header debug 1 0=off, 1=on checksum * 3 e end of message termination name example units description message id $psrf106 psrf106 protocol header datum 178 21=wgs84 178=tokyo_mean 179=tokyo_japan 180=tokyo_korea 181=tokyo_okinawa checksum * 3 2 end of message termination table 21: development data on/off example table 22: select datum example page 20 page 21
page 2 3 the receiver outputs a response to this command. the table below contains the response for the above command: $plsr,200,1,2, 3 00,1000, 3 00000, 3 0000*02 for some further examples of this command: n query the power management mode input command: $plsc,200,0*0e output response: $plsr,200,1,1*0 3 n set to full power mode input command: $plsc,200,1*0f output response: $plsr,200,1,1*0 3 name example units description mid $plsr,200 message id valid 1 0: command invalid, 1: command valid mode 2 see table 24 ontime 3 00 display when mode = 2 lp interval 1000 display when mode = 2 maxacqtime 3 00000 display when mode = 2 maxofftime 3 0000 display when mode = 2 checksum *02 end of message termination table 25: power management response example page 22 211 ? setio the table below contains the values for the following example to set gpio 1 as an input: $plsc,211,1,0,0*0f the receiver outputs a response to this command. the table below contains the response for the above command: for some further examples of this command: n set gpio 1 as an input input command: $plsc,211,1,0,0*0f output response: $plsr,211,1*1e n set gpio 1 as an output, initial state low input command: $plsc,211,1,1,0*0e output response: $plsr,211,1*1e note 1. if the message id is not recognized, the response will be ?$plsr,999,0,error*60? 2. if the value is not allowed, the response will be ?$plsr,mid,0,error*cs? 3 . all gpios default to inputs on power-up and reset. name example units description mid $plsc,211 message id gpio number 1 number of the gpio line to set. only one line can be set at a time. direction 0 direction; 0 = input; 1 = output state 0 set to 1 if the direction is an output; the value does not matter id the direction is an input. checksum *0f end of message termination table 26: setio example name example units description mid $plsr,211 message id valid 1 0: command invalid, 1: command valid checksum *1e end of message termination table 27: setio response example
page 25 page 24 212 ? readinput the table below contains the values for the following example to read the state of an input: $plsc,212,1*0c the receiver outputs a response to this command. the table below contains the response for the above command: for some further examples of this command: n read that gpio 1 is low input command: $plsc,212,1*0c output response: $plsr,212,1,0*01 n read that gpio 1 is high input command: $plsc,212,1*0c output response: $plsr,212,1,1*00 n read that gpio 1 is not an input input command: $plsc,212,1*0c output response: $plsr,212,1,2*0 3 name example units description mid $plsc,212 message id gpio number 1 number of the gpio line to read. only one line can be set at a time. checksum *0c end of message termination table 28: readinput example name example units description mid $plsr,212 message id gpio number 1 number of the gpio line to set. only one line can be set at a time. state 0 0 = low; 1 = high; 2 = the referenced gpio is not an input checksum *01 end of message termination 213 ? writeoutput the table below contains the values for the following example to write the state of gpio 1 to low: $plsc,21 3 ,1,0*11 the receiver outputs a response to this command. the table below contains the response for the above command: for some further examples of this command: n set gpio 1 to low input command: $plsc,21 3 ,1,0*11 output response: $plsr,21 3 ,1*1c n set gpio 1 to high input command: $plsc,21 3 ,1,1*10 output response: $plsr,21 3 ,1*1c n gpio 1 is not an output input command: $plsc,21 3 ,1,1*10 output response: $plsr,21 3 ,0*1d name example units description mid $plsc,21 3 message id gpio number 1 number of the gpio line to read. only one line can be set at a time. state 0 state; 0 = low; 1 = high checksum *11 end of message termination table 3 0: writeoutput example name example units description mid $plsr,21 3 message id valid 1 0: command invalid, 1: command valid checksum *1c end of message termination table 29: readinput response example table 3 1: writeoutput response example
page 26 page 27 master development system the sg series master development system provides all of the tools necessary to evaluate the sg series gps receiver module. the system includes a fully assembled development board, an active antenna, development software, and full documentation. the development board includes a power supply, a prototyping area for custom circuit development, and an oled display that shows the gps data without the need for a computer. a usb interface is also included for use with a pc running custom software or the included development software. the master development system software enables configuration of the receiver and displays the satellite data output by the receiver. the software can select from among all of the supported nmea protocols for display of the data. full documentation for the board and software is included in the development system, making integration of the module straightforward. slow start time if it?s been more than 2 months since a gps fix occurred, or the module is several hundred miles from the last fix location, the module will need to receive new almanac and ephemeris data to recalculate its new location. depending on conditions such as signal strength, distance from previous fix location, and time from last fix this process may take up to 15 minutes. satellites transmit almanac data every 15 minutes and ephemeris data every 3 0 seconds. this information should be received in wide open sky, and the module should maintain a fix for several minutes before being turned off. this will ensure that the data stored in memory is the most accurate. once a fix is established for that area, the devices can be turned on and off and maintain a very quick startup time. if the devices go for 3 to 6 hours without a fix they will need to collect the ephemeris data again which is transmitted from satellites every 3 0 seconds. figure 6: the sg series master development system figure 7: the sg series master development system software 214 ? query the table below contains the values for the following example to read the configuration and state of all of the gpio lines: $plsc,214*17 the receiver outputs a response to this command. the table below contains the response for the above command: for some further examples of this command: n set gpio 1 to low input command: $plsc,214*17 output response: $plsr,214,5,1,0,0,10,0,1,1 3 ,0,1,14,0,1,15,0,1*00 name example units description mid $plsc,214 message id checksum *17 end of message termination table 3 2: query example name example units description mid $plsr,214 message id count 5 total number of gpios gpio number 1 gpio number configuration 0 direction; 0 = input; 1 = output last state 0 0 = low; 1 = high gpio number 10 gpio number configuration 0 direction; 0 = input; 1 = output last state 1 0 = low; 1 = high gpio number 1 3 gpio number configuration 0 direction; 0 = input; 1 = output last state 1 0 = low; 1 = high gpio number 14 gpio number configuration 0 direction; 0 = input; 1 = output last state 1 0 = low; 1 = high gpio number 15 gpio number configuration 0 direction; 0 = input; 1 = output last state 1 0 = low; 1 = high checksum *00 end of message termination table 3 1: query response example
page 29 dielectric constant width/height (w/d) effective dielectric constant characteristic impedance 4.80 1.8 3 .59 50.0 4.00 2.0 3 .07 51.0 2.55 3 .0 2.12 48.0 trace board ground plane figure 8: microstrip formulas microstrip details a transmission line is a medium whereby rf energy is transferred from one place to another with minimal loss. common forms of transmission lines are coax cable, microstrip, stripline, and coplanar waveguides. since a microstrip is straightforward to understand we will focus on it here. other forms of transmission lines may also be utilized. the term ?microstrip? refers to a pcb trace running over a ground plane that is designed to serve as a transmission line. the width of the trace is based on the desired characteristic impedance of the line (in this case 50 ohms), the thickness of the pcb, and the dielectric constant of the board material. for standard 0.062in thick fr-4 board material, the trace width would be 111 mils. the correct trace width can be calculated for other widths and materials using the information below. handy software for calculating microstrip lines is also available on the linx website, www.linxtechnologies.com. there is also a variety of free programs and design tools available from other sources which can be found readily on the internet. page 28 board layout guidelines the module?s design makes integration straightforward; however, it is still critical to exercise care in pcb layout. failure to observe good layout techniques can result in a significant degradation of the module?s performance. a primary layout goal is to maintain a characteristic 50-ohm impedance throughout the path from the antenna to the module. grounding, filtering, decoupling, routing and pcb stack-up are also important considerations for any rf design. the following section provides some basic design guidelines which may be helpful. during prototyping, the module should be soldered to a properly laid-out circuit board. the use of prototyping or ?perf? boards will result in poor performance and is strongly discouraged. the module should, as much as reasonably possible, be isolated from other components on your pcb, especially high-frequency circuitry such as crystal oscillators, switching power supplies, and high-speed bus lines. when possible, separate rf and digital circuits into different pcb regions. make sure internal wiring is routed away from the module and antenna, and is secured to prevent displacement. do not route pcb traces directly under the module. there should not be any copper or traces under the module on the same layer as the module, just bare pcb. the underside of the module has traces and vias that could short or couple to traces on the product?s circuit board. the pad layout section shows a typical pcb footprint for the module. a ground plane (as large and uninterrupted as possible) should be placed on a lower layer of your pc board opposite the module. this plane is essential for creating a low impedance return for ground and consistent stripline performance. use care in routing the rf trace between the module and the antenna or connector. keep the trace as short as possible. do not pass under the module or any other component. do not route the antenna trace on multiple pcb layers as vias will add inductance. vias are acceptable for tying together ground layers and component grounds and should be used in multiples. each of the module?s ground pins should have short traces tying immediately to the ground plane through a via. bypass caps should be low esr ceramic types and located directly adjacent to the pin they are serving. a 50-ohm coax should be used for connection to an external antenna. a 50-ohm transmission line, such as a microstrip, stripline or coplanar waveguide should be used for routing rf on the pcb. the microstrip details section provides additional information. in some instances, a designer may wish to encapsulate or ?pot? the product. there is a wide variety of potting compounds with varying dielectric properties. since such compounds can considerably impact rf performance and the ability to rework or service the product, it is the responsibility of the designer to evaluate and qualify the impact and suitability of such materials. page 28 page 29
automated assembly for high-volume assembly, most users will want to auto-place the modules. the modules have been designed to maintain compatibility with reflow processing techniques; however, due to their hybrid nature, certain aspects of the assembly process are far more critical than for other component types. following are brief discussions of the three primary areas where caution must be observed. reflow temperature profile the single most critical stage in the automated assembly process is the reflow stage. the reflow profile below should not be exceeded, since excessive temperatures or transport times during reflow will irreparably damage the modules. assembly personnel will need to pay careful attention to the oven?s profile to ensure that it meets the requirements necessary to successfully reflow all components while still remaining within the limits mandated by the modules. the figure below shows the recommended reflow oven profile for the modules. shock during reflow transport since some internal module components may reflow along with the components placed on the board being assembled, it is imperative that the modules not be subjected to shock or vibration during the time solder is liquid. should a shock be applied, some internal components could be lifted from their pads, causing the module to not function properly. washability the modules are not hermetically sealed. linx recommends wash-free manufacturing; however, the modules can be subjected to a wash cycle provided that a drying time is allowed prior to applying electrical power to the modules. the drying time should be sufficient to allow any moisture that may have migrated into the module to evaporate, thus eliminating the potential for shorting damage during power-up or testing. if the wash contains contaminants, the performance may be adversely affected, even after drying. 220c he a ting r a te: 2~3c/ s ec pe a k: 240+/-0.5c prehe a t: 150~200c 120~150 s ec 25~35 s ec 60~ 8 0 s ec he a ting r a te: 2~4c/ s ec 30c temper a t u re ( c) time ( s econd s ) figure 11: maximum reflow profile pad layout the following pad layout diagram is designed to facilitate both hand and automated assembly. production guidelines the modules are housed in a hybrid smd package that supports hand and automated assembly techniques. since the modules contain discrete components internally, the assembly procedures are critical to ensuring the reliable function of the modules. the following procedures should be reviewed with and practiced by all assembly personnel. hand assembly pads located on the bottom of the module are the primary mounting surface. since these pads are inaccessible during mounting, castellations that run up the side of the module have been provided to facilitate solder wicking to the module?s underside. this allows for very quick hand soldering for prototyping and small volume production. if the recommended pad guidelines have been followed, the pads will protrude slightly past the edge of the module. use a fine soldering tip to heat the board pad and the castellation, then introduce solder to the pad at the module?s edge. the solder will wick underneath the module, providing reliable attachment. tack one module corner first and then work around the device, taking care not to exceed the times listed below. absolute maximum solder times hand-solder temp. tx +225c for 10 seconds hand-solder temp. rx +225c for 10 seconds recommended solder melting point +180c reflow oven: +240c max. (see adjoining diagram) castellations pcb pads soldering iron tip solder figure 10: soldering technique 0.02 8 (0.70) 0.036 (0.92) 0.512 (13.00) 0.050 (1.27) 0.050 (1.27) 0.036 (0.92) 0.020 (0.50) 0.045 (1.15) figure 9: recommended pcb layout page 3 0 page 3 1
linx technologies, inc. 159 ort lane merlin, or 97532 phone: (541) 471-6256 fax: (541) 471-6251 www.linxtechnologies.com u.s. corporate headquarters wireless made simple ? linx technologies is continually striving to improve the quality and function of its products. for this reason, we reserve the right to make changes to our products without notice. the information contained in this data guide is believed to be accurate as of the time of publication. specifications are based on representative lot samples. values may vary from lot-to-lot and are not guaranteed. "typical" parameters can and do vary over lots and application. linx technologies makes no guarantee, warranty, or representation regarding the suitability of any product for use in any specific application. it is the customer's responsibility to verify the suitability of the part for the intended application. no linx product is intended for use in any application where the safety of life or property is at risk. linx technologies disclaims all warranties of merchantability and fitness for a particular purpose. in no event shall linx technologies be liable for any of customer's incidental or consequential damages arising in any way from any defective or non-conforming products or for any other breach of contract by linx technologies. the limitations on linx technologies' liability are applicable to any and all claims or theories of recovery asserted by customer, including, without limitation, breach of contract, breach of warranty, strict liability, or negligence. customer assumes all liability (including, without limitation, liability for injury to person or property, economic loss, or business interruption) for all claims, including claims from third parties, arising from the use of the products. the customer will indemnify, defend, protect, and hold harmless linx technologies and its officers, employees, subsidiaries, affiliates, distributors, and representatives from and against all claims, damages, actions, suits, proceedings, demands, assessments, adjustments, costs, and expenses incurred by linx technologies as a result of or arising from any products sold by linx technologies to customer. under no conditions will linx technologies be responsible for losses arising from the use or failure of the device in any application, other than the repair, replacement, or refund limited to the original product purchase price. devices described in this publication may contain proprietary, patented, or copyrighted techniques, components, or materials. under no circumstances shall any user be conveyed any license or right to the use or ownership of such items. disclaimer ? 2010 by linx technologies, inc. the stylized linx logo, linx, ?wireless made simple?, cipherlinx, and the stylized cl logo are the trademarks of linx technologies, inc. printed in u.s.a.

▲Up To Search▲

Price & Availability of RXM-GPS-SG-T

	To Download RXM-GPS-SG-T Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .